home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX 6.5 Applications 1999 May
/
SGI IRIX 6.5 Applications 1999 May.iso
/
relnotes
/
sgimeeting
/
ch3.z
/
ch3
Wrap
Text File
|
1999-04-19
|
7KB
|
265 lines
- 1 -
3. _K_n_o_w_n__B_u_g_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s
This chapter lists known bugs and workarounds for SGImeeting
at the time of release.
3.1 _K_n_o_w_n__B_u_g_s
SGImeeting has the following known bugs:
_S_h_a_r_e_d _w_i_n_d_o_w_s _a_p_p_e_a_r _o_n _a_l_l _d_e_s_k_t_o_p_s
When using multiple desktops, windows shared from other
systems appear on all desktops. There is presently no
workaround for this.
_S_t_a_c_k_i_n_g _o_r_d_e_r _o_f _s_h_a_r_e_d _a_p_p_l_i_c_a_t_i_o_n_s _i_n_c_o_n_s_i_s_t_e_n_t
When viewing shared application from another system, it
is difficult to modify the stacking order of the shared
windows on your desktop. This is partially remedied by
using the Ctrl-Alt-F3 key sequence.
3.2 _K_n_o_w_n__L_i_m_i_t_a_t_i_o_n_s
_C_l_i_p_b_o_a_r_d _i_r_r_e_g_u_l_a_r_i_t_y
When in a conference with the "automatically share
clipboard" option set, cut and paste in non-shared
applications can display unexpected results. To avoid
this problem, do not select this option.
_F_o_c_u_s _i_r_r_e_g_u_l_a_r_i_t_y _w_h_e_n _s_h_a_r_i_n_g _a_p_p_l_i_c_a_t_i_o_n_s
When sharing applications, keyboard input focus policy
can appear inconsistent if the conference participants
are not using a policy of "click to focus". This is
caused by an implicit assumption in the T.128 protocol
that participants are using click to focus. While the
effects of this are not harmful, it can be a little bit
- 2 -
confusing to conference participants. To avoid this,
use the click to focus window manager policy in the
Desktop > Customize > Windows menu in the toolchest.
_T._1_2_7 _F_i_l_e _T_r_a_n_s_f_e_r _d_e_f_a_u_l_t_s _t_o /_t_m_p
The SGImeeting file transfer function uses a default
file location of /tmp. If a user receives a large
file, this can fill the partition containing /tmp,
which is often the root partition. To modify this,
click on the Tools > Options menu, and change the
"Store received files in" option.
_A_p_p_l_i_c_a_t_i_o_n _s_h_a_r_i_n_g _t_o _n_o_n-_S_G_I _p_l_a_t_f_o_r_m_s _l_i_m_i_t_e_d _t_o _8-_b_i_t
Applications shared with platforms other than
SGImeeting 1.0 or later are limited to 8-bit color, or
256 colors. Applications with greater visual depth are
color reduced to meet the T.128 protocol restriction.
This is true when hosting applications on all known
T.128 based platforms, including Microsoft NetMeeting.
SGImeeting 1.0 or later has an implementation of the
T.128 protocol that has been extended to support 24-bit
application support.
_O_n_l_y _o_n_e _i_n_s_t_a_n_c_e _o_f _S_G_I_m_e_e_t_i_n_g _c_a_n _r_u_n _a_t _a _t_i_m_e
Because of restrictions in the T.120 protocol, only one
copy of SGImeeting may run on a system at a time. This
restriction means that a user cannot carry on more than
one conference at a time from any one desktop, and also
means that only one user at a time may use SGImeeting
on an Octane DUO system.
_M_i_c_r_o_s_o_f_t _N_e_t_M_e_e_t_i_n_g _W_h_i_t_e_b_o_a_r_d _P_r_o_t_o_c_o_l _R_e_s_t_r_i_c_t_i_o_n_s
Microsoft NetMeeting V2.1 and earlier are limited to
the Microsoft Proprietary Whiteboard Protocol, and
cannot use the T.126 whiteboard protocol. When
collaborating with NetMeeting, T.126 whiteboard traffic
will not be visible to the NetMeeting user.
_F_u_l_l-_s_c_r_e_e_n _o_v_e_r_l_a_y_s
Some applications such as Alias|Wavefront Maya make use
of full-screen overlays to draw their popup menus.
- 3 -
When sharing such applications, the overlay regions
that appear outside the application's windows are not
visible to conference participants who are viewing the
application. This is an intended limitation for
security purposes.
_T._1_2_6 _W_h_i_t_e_b_o_a_r_d _R_e_s_t_r_i_c_t_i_o_n_s
Because of the restrictions imposed by the T.126
whiteboard protocol, some features available with the
NetMeeting proprietary whiteboard protocol are either
not available, or behave differently when using the
T.126 protocol. These include:
_T_e_x_t _e_d_i_t_i_n_g
Because the T.126 protocol does not support
text primitives, textual annotations are
rendered using bitmaps. Therefore, resulting
text cannot be edited after being completed.
_Z_o_o_m
When using the proprietary whiteboard
protocol, the zoom feature is always
synchronized with other conference
participants. This is not the case when
using the T.126 protocol.
_R_e_m_o_t_e _P_o_i_n_t_e_r_s
The semantics of remote pointers can vary on
remote systems when using the T.126 protocol.
This is due to variations in T.126
implementations.
_P_a_g_e _O_r_d_e_r_i_n_g
Page ordering in the T.126 whiteboard is not
synchronized between systems. Modifications
to the page ordering after the conference has
begun is a local operation, and does not
propagate to other participants.
- 4 -
_L_o_c_k_i_n_g
The T.126 whiteboard does not support
whiteboard locking